This solves the issue for the worker module itself, but not its dependencies. I.e. if a worker module imports/requires another module, modifying the latter still does not trigger re-run.

I have updated changes to watch dependencies for worker as well, so changes in imported/required modules will now trigger a re-run.
@clemyan

This is the wrong way to solve this, for a myriad of reasons: (based on a cursory glance of the code. Did not bother to actual test it)

1. It is impossible to properly parse JS with regex. This approach cannot even distinguish if the "import" is part of a string or a comment
2. It only works for direct dependencies of the worker module, not transitively. (I.e. it does not watch dependencies of dependencies, and their dependencies, etc.)
3. It only works for literals specifiers that are relative paths, not for absolute paths require('/path/to/file.js'), packages require('my-pkg/sub/path'), dynamic specifier require('./messages/'+language+'/string.json'), or paths that are resolved by customization hooks
4. What about the worker module itself? If it is loaded by customization hooks, there isn't necessarily a file on disk to readSync from.

Any solution must be integrated into Node's loading pipeline

I will revert back these updates and work on the suggestions
@clemyan

@clemyan
I have updated handling of dependencies from worker thread. For this I have also reverted my changes from the initial commit as well f9beab0
I have implemented the solution for both cjs and esm files.
Do let me know your feedback on the proposed solution and whether it makes sense to proceed further in this direction.

The added test already passes on main, that means either the code change is not necessary, or that it's not actually testing what you're trying to achieve

Sure!! @aduh95 I will update the tests for this. Thanks for your feedback!!

@aduh95 Please do review the updated tests for the proposed changes based on behaviour of worker file and it's dependencies in --watch mode for both cjs and esm modules.

Can you not put the tests in test/sequential/test-watch-mode.mjs? That file is enormous, which is becoming a maintenance issue/

@aduh95 As suggested I have removed tests from test/sequential/test-watch-mode.mjs to a new file and made few lint fixes.
Do let me know if any further changes are required

Codecov Report

❌ Patch coverage is 93.61702% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.71%. Comparing base (4b3d82c) to head (f7a05a3).
⚠️ Report is 1 commits behind head on main.

@@           Coverage Diff           @@
##             main   #62368   +/-   ##
=======================================
  Coverage   89.70%   89.71%           
=======================================
  Files         695      695           
  Lines      214476   214523   +47     
  Branches    41072    41075    +3     
=======================================
+ Hits       192405   192464   +59     
+ Misses      14115    14109    -6     
+ Partials     7956     7950    -6